Release 10.1A: OpenEdge Getting Started:
Database Essentials

Relative- and absolute-path databases

OpenEdge databases can be either relative-path or absolute-path:

Relative-path databases — Relative-path databases are the simplest form of OpenEdge databases. They are made up of a minimum number of files. A relative-path database stores all extents associated with the database in the same directory as the control area. The control area contains relative paths to all the extents. You would use a relative-path database in the following situations:
When the database must be opened across a network for demonstration purposes.
When the database must be copied with OS tools, as when installing a demonstration database.
When the database is the master database to be associated with a new application.

Use the PRODB utility to create a relative-path database from an empty database. If you use PROSTRCT with the LIST qualifier after creating the relative-path database, you will see a dot at the start of each extent name. The dot indicates a relative path.

Schema must be loaded into an empty relative-path database to make it useful. Any standard technique for loading schema, such as dump and load or PROCOPY, can be used. The database maintains its relative path as long as its structure is not changed. As soon as areas or extents are added, the database becomes an absolute-path database.

Absolute-path databases — Absolute-path databases are used in most production situations. With an absolute-path database, extents associated with the database can be stored anywhere on your system. The control area contains absolute paths to each extent. Absolute-path databases should not be copied using OS tools; rather, PROBKUP and PROCOPY should be used so that all underlying files are properly backed up or copied.